This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Sametime 3 LDAP authentication ~Lily Prefoomanader 28.Mar.03 04:08 AM a Web browser Sametime Administration 3.0Windows NT/2000
You seem to have a very similar situation to mine. I have Domino 5.0.11/ST 30 SP1 that was tested as a Domino directory first due to problems logging in as admin. After resolving that problem I went to convert to a LDAP directory.
"Sametime 2.x/3.0: How to Change Your Sametime Server from Domino to LDAP After Installation" (#187422).
The first night I followed the steps to convert from Domino to Ldap it worked. I saw LDAP Directory in the ST WEB Admin configuration screen. The next day I had a to reboot the server and it went back to Domino diectory on the WEB Admin Screen.
I tested user authentication and it is actually using the Domino directory to authenticate ST users. Even though the ST server is also bounded to the LDAP server as an authenticated user. (We verified this
I found another Lotus document that said there was another step to this that was not published in the STADMIN Guide. Copy the dll files from the Directory BB\LDAP to the Domino\Data dir. That didn't work either...
"Sametime 3.0: How to Change Your Sametime Server from LDAP to Domino Directory Authentication" (#1099669).
Then tried... Edit the SAMETIME.INI file.
"Sametime 3.x: Issues When Changing Directory Type from Domino to LDAP for Authentication" (#1088396).
Under the [Directory] section of the file, add the line: ST_DB_LDAP_HOMESERVER_NOTES_FORMAT=1
Still no change... I will rebuild the server again and choose LDAP as it loads ST 30.
I am interested in how you successfully got yours to work and what your ST LDAPServer document search config is setup like. WE also use Novell LDAP search and authentication. Or hope to some day...